In response to this:

Since go.mod was updated to use Go 1.25 the 1.24 builder image we were using is no longer valid.
The go version bump updated all the required CI images but left the dev one in the Makefile with the previous content.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

• Update dev runtime Go image from 1.24 to 1.25
• Align Makefile with go.mod Go version requirement
• Update OpenShift release image to version 4.22

Update dev Go image to 1.25

• Updated RUNTIME_IMAGE_NAME variable from Go 1.24 to Go 1.25
• Changed OpenShift release version from 4.20 to 4.22
• Aligns dev environment with go.mod Go version requirement

Makefile

Description

The updated RUNTIME_IMAGE_NAME uses a mutable tag (no digest pin). If the registry tag is ever
re-pushed, container-based verify/generate runs can become non-reproducible and unexpectedly change
behavior across developers/machines.

Code

Makefile[7]

+RUNTIME_IMAGE_NAME ?= registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.25-openshift-4.22

Evidence

The Makefile sets RUNTIME_IMAGE_NAME to a tag (not a digest) and uses it directly to run
verification and generation in a container, so any tag mutation changes the environment used by
these workflows.

Makefile[6-8]
Makefile[172-176]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`RUNTIME_IMAGE_NAME` is set to a mutable tag. This makes `make verify-with-container` and `make generate-with-container` non-reproducible if the tag content changes over time.

### Issue Context
The Makefile runs verification/generation inside the image referenced by `$(RUNTIME_IMAGE_NAME)`, so the exact image content matters for deterministic results.

### Fix Focus Areas
- Makefile[6-8]
- Makefile[172-176]

### Suggested change
- Update `RUNTIME_IMAGE_NAME` to include a digest, e.g.:
 - `registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.25-openshift-4.22@sha256:<digest>`
- Optionally keep the tag in a separate variable and append `@$(RUNTIME_IMAGE_DIGEST)` when set.
- Add a short comment documenting how to obtain the digest (e.g., via `skopeo inspect docker://...`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

Walkthrough

The RUNTIME_IMAGE_NAME variable in the Makefile was updated to reference a newer base image. The change updates the Go version from 1.24 to 1.25 and the OpenShift release version from 4.20 to 4.22. The updated image tag is used as the default container runtime image during the build process.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

• OWNERS [JoelSpeed]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

In response to this:

/retest
/verified by CI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.